Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2e5299bf0b131bf57fde406abc47c23d48b9b0da76ff7f9ca36c1e8c9f98e99

Tx prefix hash: 0bb417257e3841c7d08d62afb7bb13730c3460e6c61efbb56d714d10897eacf1
Tx public key: f14235c143f8da0875b109dce64bca3a54694822b33c7ea59340e7b5beb50853
Timestamp: 1723179577 Timestamp [UCT]: 2024-08-09 04:59:37 Age [y:d:h:m:s]: 00:242:06:11:18
Block: 1083916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173021 RingCT/type: yes/0
Extra: 01f14235c143f8da0875b109dce64bca3a54694822b33c7ea59340e7b5beb5085302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cfec70578df88ebe4d972d05ed7e313599033dc66067ef5c6a402e8fd69b308 0.600000000000 1558003 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": 1083926, "vin": [ { "gen": { "height": 1083916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cfec70578df88ebe4d972d05ed7e313599033dc66067ef5c6a402e8fd69b308" } } ], "extra": [ 1, 241, 66, 53, 193, 67, 248, 218, 8, 117, 177, 9, 220, 230, 75, 202, 58, 84, 105, 72, 34, 179, 60, 126, 165, 147, 64, 231, 181, 190, 181, 8, 83, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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