Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b27a28fe3aec2fd7634ca945e61da58c589b9f9e802b956fc9fe315d3fbaf9b

Tx prefix hash: adf247bb04994aceeed2a22fd6ceee82092ce9cc9cc8942f225a2e629d632cf1
Tx public key: 98f0e90414a71777afcacc5d6333f0fda37eff91d3259581c02afa5924d28c40
Timestamp: 1706592787 Timestamp [UCT]: 2024-01-30 05:33:07 Age [y:d:h:m:s]: 01:287:14:25:59
Block: 946378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464357 RingCT/type: yes/0
Extra: 0198f0e90414a71777afcacc5d6333f0fda37eff91d3259581c02afa5924d28c400211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f67dce0e666044b3d6f858c313c613de4a0a01a5f35f730aa1a50bd10d80c79 0.600000000000 1404710 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": 946388, "vin": [ { "gen": { "height": 946378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f67dce0e666044b3d6f858c313c613de4a0a01a5f35f730aa1a50bd10d80c79" } } ], "extra": [ 1, 152, 240, 233, 4, 20, 167, 23, 119, 175, 202, 204, 93, 99, 51, 240, 253, 163, 126, 255, 145, 211, 37, 149, 129, 192, 42, 250, 89, 36, 210, 140, 64, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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