Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d813c342ba9ca2111c5b95c3b24661af947ef2609c22b27f5f8980843e84d397

Tx prefix hash: c55317165f8f96ddff67e608eb6c69d044f37ec2ef3a6278aa811f54ca75864e
Tx public key: 51454e7f3f2d2cbba97c4af8bfc4e7a3c3f4db9a16487cd79ea97a74dba1a746
Timestamp: 1728614957 Timestamp [UCT]: 2024-10-11 02:49:17 Age [y:d:h:m:s]: 00:044:15:36:50
Block: 1128977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31883 RingCT/type: yes/0
Extra: 0151454e7f3f2d2cbba97c4af8bfc4e7a3c3f4db9a16487cd79ea97a74dba1a746021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a1f69affc732e698ac4940b8dd7ab924bbe06483715d5be13bc747ade7bc251 0.600000000000 1611800 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": 1128987, "vin": [ { "gen": { "height": 1128977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a1f69affc732e698ac4940b8dd7ab924bbe06483715d5be13bc747ade7bc251" } } ], "extra": [ 1, 81, 69, 78, 127, 63, 45, 44, 187, 169, 124, 74, 248, 191, 196, 231, 163, 195, 244, 219, 154, 22, 72, 124, 215, 158, 169, 122, 116, 219, 161, 167, 70, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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