Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 889bf5c64ad9cd972423f646dd47fbff1a23d479b00cd3b6e8a066aae53f8d4c

Tx prefix hash: b65caae2d3d3d35f38150b03375affdc2df69962445d5bed1d10aec816920fe8
Tx public key: fe72a0f226930a3370e66d4ed139ac6f3e4997e2ef431d1337bbc51db653cc18
Timestamp: 1708950102 Timestamp [UCT]: 2024-02-26 12:21:42 Age [y:d:h:m:s]: 01:084:07:56:37
Block: 965953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321321 RingCT/type: yes/0
Extra: 01fe72a0f226930a3370e66d4ed139ac6f3e4997e2ef431d1337bbc51db653cc1802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65aeaac92b76c252c7b5e9f1ca2a5f2a54ee539cda2f1db64180988bf9b4c371 0.600000000000 1425708 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": 965963, "vin": [ { "gen": { "height": 965953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65aeaac92b76c252c7b5e9f1ca2a5f2a54ee539cda2f1db64180988bf9b4c371" } } ], "extra": [ 1, 254, 114, 160, 242, 38, 147, 10, 51, 112, 230, 109, 78, 209, 57, 172, 111, 62, 73, 151, 226, 239, 67, 29, 19, 55, 187, 197, 29, 182, 83, 204, 24, 2, 17, 0, 0, 0, 1, 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