Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5185f566bdb2e0527c9a671e4100d5b673801f4cc4f4040e7f24c0de1f43dcf

Tx prefix hash: 6a8f424bfcd862128f2ab3d6b529204fd512d8d236a88d03e4081efcd52ad608
Tx public key: 790dc19eea39401ae2bebadd84d7b362df456779f4791359f18cfa59105c6206
Timestamp: 1703005048 Timestamp [UCT]: 2023-12-19 16:57:28 Age [y:d:h:m:s]: 02:016:00:03:06
Block: 916672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531214 RingCT/type: yes/0
Extra: 01790dc19eea39401ae2bebadd84d7b362df456779f4791359f18cfa59105c6206021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3179812c79e44ff76f971e0d50daca08a5d7b6a0be5b5918b52f9a88dd11d1b8 0.600000000000 1374232 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": 916682, "vin": [ { "gen": { "height": 916672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3179812c79e44ff76f971e0d50daca08a5d7b6a0be5b5918b52f9a88dd11d1b8" } } ], "extra": [ 1, 121, 13, 193, 158, 234, 57, 64, 26, 226, 190, 186, 221, 132, 215, 179, 98, 223, 69, 103, 121, 244, 121, 19, 89, 241, 140, 250, 89, 16, 92, 98, 6, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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