Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b74dea9c3c28be003a205f46f4e3754a2a054993833dff9344ff13e281d962e6

Tx prefix hash: e39249a5b102d6f5b0c32c6cfcef719f40add837eeb08cf1168c662956fc0cf0
Tx public key: ba6581db9e705d31fe9190c2d0f33cf1473776e5117a39fc3ed0566c1469445e
Timestamp: 1699771724 Timestamp [UCT]: 2023-11-12 06:48:44 Age [y:d:h:m:s]: 01:143:13:10:58
Block: 889864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363757 RingCT/type: yes/0
Extra: 01ba6581db9e705d31fe9190c2d0f33cf1473776e5117a39fc3ed0566c1469445e02110000000474c3735f000000000000000000

1 output(s) for total of 0.691052697000 dcy

stealth address amount amount idx
00: fed44ccbeecb52dc2035e1b357d1c9c885e38202258af65ae4a1266c0a18e4c1 0.691052697000 1345881 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": 889874, "vin": [ { "gen": { "height": 889864 } } ], "vout": [ { "amount": 691052697, "target": { "key": "fed44ccbeecb52dc2035e1b357d1c9c885e38202258af65ae4a1266c0a18e4c1" } } ], "extra": [ 1, 186, 101, 129, 219, 158, 112, 93, 49, 254, 145, 144, 194, 208, 243, 60, 241, 71, 55, 118, 229, 17, 122, 57, 252, 62, 208, 86, 108, 20, 105, 68, 94, 2, 17, 0, 0, 0, 4, 116, 195, 115, 95, 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