Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29140babb31fa107fe34b9a0957a1e3bb4076fcbec2d941b7b3b5b0ca2bc263f

Tx prefix hash: 0ebc97555d22b446f11bd8d2268fafe827b2ca47f65efaa13831a2a87561fdb2
Tx public key: 5b2f0c9a8da0040e8098d59bf087e5b79ec8592104c17a44f2f3961f790c0008
Timestamp: 1761611402 Timestamp [UCT]: 2025-10-28 00:30:02 Age [y:d:h:m:s]: 00:071:03:05:58
Block: 1399432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50913 RingCT/type: yes/0
Extra: 015b2f0c9a8da0040e8098d59bf087e5b79ec8592104c17a44f2f3961f790c000802110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cd52b65cf72193b5652524227ab2822faae5eacad5ffbddfa243f1aaea7c130 0.600000000000 1887737 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": 1399442, "vin": [ { "gen": { "height": 1399432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cd52b65cf72193b5652524227ab2822faae5eacad5ffbddfa243f1aaea7c130" } } ], "extra": [ 1, 91, 47, 12, 154, 141, 160, 4, 14, 128, 152, 213, 155, 240, 135, 229, 183, 158, 200, 89, 33, 4, 193, 122, 68, 242, 243, 150, 31, 121, 12, 0, 8, 2, 17, 0, 0, 0, 4, 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