Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef47c6253cd522e80f0c7086d856ea255f2558658daf926af7ef6b0ffc9fa0f

Tx prefix hash: 195feba5ffebf3f6cb034b87f39778fde8224e2435f279f2ac4cf6416132f4bb
Tx public key: e99c39c7457ab1cdf6c336f992cbf86313079f336bbb9e82e3d0b875fa48e437
Timestamp: 1735654231 Timestamp [UCT]: 2024-12-31 14:10:31 Age [y:d:h:m:s]: 01:004:23:50:34
Block: 1187207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262019 RingCT/type: yes/0
Extra: 01e99c39c7457ab1cdf6c336f992cbf86313079f336bbb9e82e3d0b875fa48e437021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4477faf34872c2b45a4519811ec3c45ad819ce277f2d5bb4d2b444fc5280f3a8 0.600000000000 1673694 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": 1187217, "vin": [ { "gen": { "height": 1187207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4477faf34872c2b45a4519811ec3c45ad819ce277f2d5bb4d2b444fc5280f3a8" } } ], "extra": [ 1, 233, 156, 57, 199, 69, 122, 177, 205, 246, 195, 54, 249, 146, 203, 248, 99, 19, 7, 159, 51, 107, 187, 158, 130, 227, 208, 184, 117, 250, 72, 228, 55, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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