Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 541d0d0def1e9965c9a7bc2c744750e6be241227bc057a6fe46ae4fde33b4154

Tx prefix hash: 314f6052998ee5df3a8780cc0d2375d170ad0315fd38e7a4bce7acbf7b569683
Tx public key: 4dd996e2e32d7f36f07965a7826dacea86393e9bae95f19c24c0ff9072628415
Timestamp: 1648480745 Timestamp [UCT]: 2022-03-28 15:19:05 Age [y:d:h:m:s]: 02:352:01:44:20
Block: 468279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 770981 RingCT/type: yes/0
Extra: 014dd996e2e32d7f36f07965a7826dacea86393e9bae95f19c24c0ff90726284150211000000014da16a3a000000000000000000

1 output(s) for total of 17.234454156000 dcy

stealth address amount amount idx
00: 5d04a9efa23b141b72e3a8a121b8a8096e30b7af6a3acb3659815539709d9ddb 17.234454156000 886967 of 0

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": 468289, "vin": [ { "gen": { "height": 468279 } } ], "vout": [ { "amount": 17234454156, "target": { "key": "5d04a9efa23b141b72e3a8a121b8a8096e30b7af6a3acb3659815539709d9ddb" } } ], "extra": [ 1, 77, 217, 150, 226, 227, 45, 127, 54, 240, 121, 101, 167, 130, 109, 172, 234, 134, 57, 62, 155, 174, 149, 241, 156, 36, 192, 255, 144, 114, 98, 132, 21, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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