Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 702a4fdba9f45a3509a26de1a886f70574c33b36779d436e86aeb3063cf2d507

Tx prefix hash: 5735ac9a3c8db965b4f7c19e823073cf21a9fd7972b9da402d10b8b1e072defd
Tx public key: f273a6b61a794184cfc75b3d79f16f0440e8f9ca12f1afee3df1ec830a1c89d2
Timestamp: 1704575641 Timestamp [UCT]: 2024-01-06 21:14:01 Age [y:d:h:m:s]: 01:308:19:57:47
Block: 929664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479555 RingCT/type: yes/0
Extra: 01f273a6b61a794184cfc75b3d79f16f0440e8f9ca12f1afee3df1ec830a1c89d202110000001259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e81d1f50af7c35e449e44abfb64981ab09f43f6aec66c41d354294e87a4982b1 0.600000000000 1387540 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 929674, "vin": [ { "gen": { "height": 929664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e81d1f50af7c35e449e44abfb64981ab09f43f6aec66c41d354294e87a4982b1" } } ], "extra": [ 1, 242, 115, 166, 182, 26, 121, 65, 132, 207, 199, 91, 61, 121, 241, 111, 4, 64, 232, 249, 202, 18, 241, 175, 238, 61, 241, 236, 131, 10, 28, 137, 210, 2, 17, 0, 0, 0, 18, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8