Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27300243456470a7afc32752ee141ef9580a999450c44e0f463fffbdb94dea41

Tx prefix hash: e4f58f00e95ba157e6cbc6ba28a43c2643da30e8dbdfc6bc45eeebab2562ad9e
Tx public key: ae784de883a7d4a7bf79cb6e32aa4ae171ede0c5acb0d4fa6edef907aed6b85b
Timestamp: 1698878327 Timestamp [UCT]: 2023-11-01 22:38:47 Age [y:d:h:m:s]: 01:152:08:14:48
Block: 882648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369866 RingCT/type: yes/0
Extra: 01ae784de883a7d4a7bf79cb6e32aa4ae171ede0c5acb0d4fa6edef907aed6b85b021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.730164611000 dcy

stealth address amount amount idx
00: a7c1f21f37c4188decc6abf3d36e64e9df7885efbfca3d3bd1a9f4607ef71211 0.730164611000 1338320 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": 882658, "vin": [ { "gen": { "height": 882648 } } ], "vout": [ { "amount": 730164611, "target": { "key": "a7c1f21f37c4188decc6abf3d36e64e9df7885efbfca3d3bd1a9f4607ef71211" } } ], "extra": [ 1, 174, 120, 77, 232, 131, 167, 212, 167, 191, 121, 203, 110, 50, 170, 74, 225, 113, 237, 224, 197, 172, 176, 212, 250, 110, 222, 249, 7, 174, 214, 184, 91, 2, 17, 0, 0, 0, 3, 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