Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c5253ebb492f037ad74897b201869954fe41d1fc287bd34f8eecf67a83fa1c9

Tx prefix hash: 906d7a75502f599c0762403f5ab93a726ec9db034fa78820c3a3ecd3c8be3dc8
Tx public key: 9a43ef9b740927a9925fbff26c1538371c714fc72c7535b52f31084273c93c8d
Timestamp: 1761656501 Timestamp [UCT]: 2025-10-28 13:01:41 Age [y:d:h:m:s]: 00:069:09:42:41
Block: 1399801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49704 RingCT/type: yes/0
Extra: 019a43ef9b740927a9925fbff26c1538371c714fc72c7535b52f31084273c93c8d02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bdf3ef4910384b4c2600c06ea36fb99bf3a0f99f4b2633e5ecbcbf68a1b78f4 0.600000000000 1888106 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": 1399811, "vin": [ { "gen": { "height": 1399801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bdf3ef4910384b4c2600c06ea36fb99bf3a0f99f4b2633e5ecbcbf68a1b78f4" } } ], "extra": [ 1, 154, 67, 239, 155, 116, 9, 39, 169, 146, 95, 191, 242, 108, 21, 56, 55, 28, 113, 79, 199, 44, 117, 53, 181, 47, 49, 8, 66, 115, 201, 60, 141, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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