Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5679df680e58e6774b2d6558c699ba89f5e6e9fa661c624ec106fe65412e4dc

Tx prefix hash: c0c29aa1d2e329add255f157a5a4e4b3232a7f11899eb14ae70b277290f9b15e
Tx public key: 0546e47c3b43e266cb37b99ca7aff055853e2e5722f1cbf192ee8614f800bad7
Timestamp: 1737801732 Timestamp [UCT]: 2025-01-25 10:42:12 Age [y:d:h:m:s]: 00:143:05:46:51
Block: 1204948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102116 RingCT/type: yes/0
Extra: 010546e47c3b43e266cb37b99ca7aff055853e2e5722f1cbf192ee8614f800bad7021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52d5360694d93079a32a7d48ab2abe6bb592c836e215aeeab23c77a9643b0a04 0.600000000000 1691643 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": 1204958, "vin": [ { "gen": { "height": 1204948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52d5360694d93079a32a7d48ab2abe6bb592c836e215aeeab23c77a9643b0a04" } } ], "extra": [ 1, 5, 70, 228, 124, 59, 67, 226, 102, 203, 55, 185, 156, 167, 175, 240, 85, 133, 62, 46, 87, 34, 241, 203, 241, 146, 238, 134, 20, 248, 0, 186, 215, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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