Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44c7e96297246f578228326bd737e5ff63ae9cb68fd8d033e6f1681f33f138d

Tx prefix hash: b7a6de7f49d11df78c6c7dc58ad240aa82897d73d7bd234fe04539ead0493457
Tx public key: 2fcfd7b5928dc88ade7e610e217a4b96ed10826db36b65ca53cd34f89124eb4e
Timestamp: 1736600304 Timestamp [UCT]: 2025-01-11 12:58:24 Age [y:d:h:m:s]: 00:112:15:14:14
Block: 1195034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80299 RingCT/type: yes/0
Extra: 012fcfd7b5928dc88ade7e610e217a4b96ed10826db36b65ca53cd34f89124eb4e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2cb12eac6ff5cddaf58668d3ce71214abf79892e97d57cb5307162928a561cf 0.600000000000 1681619 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": 1195044, "vin": [ { "gen": { "height": 1195034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2cb12eac6ff5cddaf58668d3ce71214abf79892e97d57cb5307162928a561cf" } } ], "extra": [ 1, 47, 207, 215, 181, 146, 141, 200, 138, 222, 126, 97, 14, 33, 122, 75, 150, 237, 16, 130, 109, 179, 107, 101, 202, 83, 205, 52, 248, 145, 36, 235, 78, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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