Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b02624701a148ff905387372f63a2f80f38e828fde514f88d251828643cc050

Tx prefix hash: 4b3176834ff78281f703b776a1c902faa1d4a34c9080ce38ea99a7bbfdc4180e
Tx public key: 9f5d0ff2e4cd43ec5a3475121440b78d2e76fadca7e47d313a938b4a66da26dd
Timestamp: 1741063204 Timestamp [UCT]: 2025-03-04 04:40:04 Age [y:d:h:m:s]: 00:334:17:17:21
Block: 1231713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236903 RingCT/type: yes/0
Extra: 019f5d0ff2e4cd43ec5a3475121440b78d2e76fadca7e47d313a938b4a66da26dd021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b30adcc40d76cbd68c704793d21ca2d17e46e58c041ced4646c9d18e28f157a5 0.600000000000 1718624 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": 1231723, "vin": [ { "gen": { "height": 1231713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b30adcc40d76cbd68c704793d21ca2d17e46e58c041ced4646c9d18e28f157a5" } } ], "extra": [ 1, 159, 93, 15, 242, 228, 205, 67, 236, 90, 52, 117, 18, 20, 64, 183, 141, 46, 118, 250, 220, 167, 228, 125, 49, 58, 147, 139, 74, 102, 218, 38, 221, 2, 17, 0, 0, 0, 5, 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