Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e09c8a6cedab31dafd7455bddcbd4fe091a94197a1327872266d757ffe1682b

Tx prefix hash: 735b730315d0ba391e3aba7f0c853afae2325cb1cd1dd6f17e4daef5fa7a0a86
Tx public key: 9930fe65acac2f4b49cf2bfdfac32921ae6921458a2a26deb0044cce3ae98b25
Timestamp: 1724886089 Timestamp [UCT]: 2024-08-28 23:01:29 Age [y:d:h:m:s]: 00:227:17:40:54
Block: 1098061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162635 RingCT/type: yes/0
Extra: 019930fe65acac2f4b49cf2bfdfac32921ae6921458a2a26deb0044cce3ae98b2502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd7eff27f8a2d5c761a0d0ef0ac30314c968ee123ef53277d0e10c2df92d82ec 0.600000000000 1573648 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": 1098071, "vin": [ { "gen": { "height": 1098061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd7eff27f8a2d5c761a0d0ef0ac30314c968ee123ef53277d0e10c2df92d82ec" } } ], "extra": [ 1, 153, 48, 254, 101, 172, 172, 47, 75, 73, 207, 43, 253, 250, 195, 41, 33, 174, 105, 33, 69, 138, 42, 38, 222, 176, 4, 76, 206, 58, 233, 139, 37, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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