Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a390c828bbc6bd8ad2ae07149f46a6435b77d550403700c0c105edefc591efc2

Tx prefix hash: b1fb9a3602bc827794cc55358044ec3b372147edb06953ce1e3e8d5988f471d6
Tx public key: b77b046d5b27c6d8eb64e17b927ec79981adfcfc39a3070eb1e905a2a9390b2b
Timestamp: 1745641523 Timestamp [UCT]: 2025-04-26 04:25:23 Age [y:d:h:m:s]: 00:242:00:12:41
Block: 1269616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170723 RingCT/type: yes/0
Extra: 01b77b046d5b27c6d8eb64e17b927ec79981adfcfc39a3070eb1e905a2a9390b2b02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc847c547911c05ee19402805fd679e1f2791ae2ae8bfb4badc78cb845ee4626 0.600000000000 1756855 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": 1269626, "vin": [ { "gen": { "height": 1269616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc847c547911c05ee19402805fd679e1f2791ae2ae8bfb4badc78cb845ee4626" } } ], "extra": [ 1, 183, 123, 4, 109, 91, 39, 198, 216, 235, 100, 225, 123, 146, 126, 199, 153, 129, 173, 252, 252, 57, 163, 7, 14, 177, 233, 5, 162, 169, 57, 11, 43, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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