Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21731a121628f054e9a4e20d6f866a75d350039688418f3d075f297493fedd2a

Tx prefix hash: 4af1e8216a8d4f6d0ad61db7caa5656ff909a1c9c11ee0e7a03005077d62aa54
Tx public key: 6aae45c7c2c869882bdaee966633aa9e51866c310654c1f72c67c3654030f681
Timestamp: 1711704183 Timestamp [UCT]: 2024-03-29 09:23:03 Age [y:d:h:m:s]: 00:287:09:12:48
Block: 988793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205700 RingCT/type: yes/0
Extra: 016aae45c7c2c869882bdaee966633aa9e51866c310654c1f72c67c3654030f68102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d2109e0ea1677eedf99529cc1cb150c3fba2eb2d8917fcbcdb7771306fdca55 0.600000000000 1449078 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": 988803, "vin": [ { "gen": { "height": 988793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d2109e0ea1677eedf99529cc1cb150c3fba2eb2d8917fcbcdb7771306fdca55" } } ], "extra": [ 1, 106, 174, 69, 199, 194, 200, 105, 136, 43, 218, 238, 150, 102, 51, 170, 158, 81, 134, 108, 49, 6, 84, 193, 247, 44, 103, 195, 101, 64, 48, 246, 129, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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