Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7da32b3ef8c6c393f236616382ce7a0a985cf018ce967a0e2af136cb3b818d8

Tx prefix hash: 006b4fb4b684a5377157ef503c342097115fbfe8a39bbed93c987badceb72858
Tx public key: 5c01ae0b30df74741f8221a25b6074356f29730f8168eeb649e51d5a8e9f72f8
Timestamp: 1721256757 Timestamp [UCT]: 2024-07-17 22:52:37 Age [y:d:h:m:s]: 00:260:07:11:06
Block: 1067987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185947 RingCT/type: yes/0
Extra: 015c01ae0b30df74741f8221a25b6074356f29730f8168eeb649e51d5a8e9f72f8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9413c99f3e7580dc568a3c0aa30c00b5b354b30013e2aa168e9488496d6aafa5 0.600000000000 1538956 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": 1067997, "vin": [ { "gen": { "height": 1067987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9413c99f3e7580dc568a3c0aa30c00b5b354b30013e2aa168e9488496d6aafa5" } } ], "extra": [ 1, 92, 1, 174, 11, 48, 223, 116, 116, 31, 130, 33, 162, 91, 96, 116, 53, 111, 41, 115, 15, 129, 104, 238, 182, 73, 229, 29, 90, 142, 159, 114, 248, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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