Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fe86e0c86b24122b04dbfd05fe06ce53c9a651b66360c289628f912b0c8a55e

Tx prefix hash: 5cfc2050d17ab1ff13200619090c683e0ea2ecdffe1a020f1018bc9697c872d2
Tx public key: 655345480a2ba1b935869b3a2458fdcaa752bb1114ed22f4ffc54dcbd2cdb297
Timestamp: 1754977302 Timestamp [UCT]: 2025-08-12 05:41:42 Age [y:d:h:m:s]: 00:054:19:24:25
Block: 1345253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38413 RingCT/type: yes/0
Extra: 01655345480a2ba1b935869b3a2458fdcaa752bb1114ed22f4ffc54dcbd2cdb297021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f2eab2ccd01587d4d4e20a7d69f5e2e91d92085a62051477e85a0ffce6e2794 0.600000000000 1833144 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": 1345263, "vin": [ { "gen": { "height": 1345253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f2eab2ccd01587d4d4e20a7d69f5e2e91d92085a62051477e85a0ffce6e2794" } } ], "extra": [ 1, 101, 83, 69, 72, 10, 43, 161, 185, 53, 134, 155, 58, 36, 88, 253, 202, 167, 82, 187, 17, 20, 237, 34, 244, 255, 197, 77, 203, 210, 205, 178, 151, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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