Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a58b8f237f44bcd97a9cd4b13969191f3a6ed7e9757b5605444811af91fbdc7a

Tx prefix hash: 26846eae393f48ad13487e1de5a651b3a9c6e4f79fa112be9e51f5d221c35cd3
Tx public key: b72c527cff9922741477caf6d61de150af70b1d5f16d86d2a1b8e54826581a02
Timestamp: 1740832112 Timestamp [UCT]: 2025-03-01 12:28:32 Age [y:d:h:m:s]: 00:264:15:36:32
Block: 1229795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186897 RingCT/type: yes/0
Extra: 01b72c527cff9922741477caf6d61de150af70b1d5f16d86d2a1b8e54826581a02021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eb8ffd47af99308d9c932de60e6bee6cf18bb3e5b7cfc6c1d41977afa6685f5 0.600000000000 1716684 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": 1229805, "vin": [ { "gen": { "height": 1229795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eb8ffd47af99308d9c932de60e6bee6cf18bb3e5b7cfc6c1d41977afa6685f5" } } ], "extra": [ 1, 183, 44, 82, 124, 255, 153, 34, 116, 20, 119, 202, 246, 214, 29, 225, 80, 175, 112, 177, 213, 241, 109, 134, 210, 161, 184, 229, 72, 38, 88, 26, 2, 2, 17, 0, 0, 0, 2, 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