Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119770f2f5ca9dbb9b69e711c0fccabd0ff9d9222b5fa327d618a0de5a98eff4

Tx prefix hash: 4ccfefc12e849479665af7eca4a8ec0f57ac9a5dccd94d2623e36840d4bc5d77
Tx public key: ce15a46c480573d317fe5fb605f64b2a167cd2d6e15b487011dfd4ffe307492a
Timestamp: 1730020334 Timestamp [UCT]: 2024-10-27 09:12:14 Age [y:d:h:m:s]: 00:027:18:34:01
Block: 1140593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19836 RingCT/type: yes/0
Extra: 01ce15a46c480573d317fe5fb605f64b2a167cd2d6e15b487011dfd4ffe307492a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c0a6e1a3e06653447bd60d3726a2230bfbbd2d29c16ffc7f872b9cbf061e413 0.600000000000 1624394 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": 1140603, "vin": [ { "gen": { "height": 1140593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c0a6e1a3e06653447bd60d3726a2230bfbbd2d29c16ffc7f872b9cbf061e413" } } ], "extra": [ 1, 206, 21, 164, 108, 72, 5, 115, 211, 23, 254, 95, 182, 5, 246, 75, 42, 22, 124, 210, 214, 225, 91, 72, 112, 17, 223, 212, 255, 227, 7, 73, 42, 2, 17, 0, 0, 0, 1, 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