Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1e8daefda11292029162e6a0a84404c5075400b5829d25cdd387fcf8ff0d432

Tx prefix hash: ee998637f4a2b0fcef868a6a2a7236b991af12dcc715b0d2fba03fa6e9647afb
Tx public key: e5b8fd7a6c27e8e2447ff16c84a050d2e314e645c97f57081c89ee25ef509337
Timestamp: 1726702650 Timestamp [UCT]: 2024-09-18 23:37:30 Age [y:d:h:m:s]: 00:202:12:16:33
Block: 1113126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144562 RingCT/type: yes/0
Extra: 01e5b8fd7a6c27e8e2447ff16c84a050d2e314e645c97f57081c89ee25ef509337021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d276192f13b4ab34db3df25d3da03e0eb6e1b1b95c77eab5e3ddcbb7b5f8ef5 0.600000000000 1592685 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": 1113136, "vin": [ { "gen": { "height": 1113126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d276192f13b4ab34db3df25d3da03e0eb6e1b1b95c77eab5e3ddcbb7b5f8ef5" } } ], "extra": [ 1, 229, 184, 253, 122, 108, 39, 232, 226, 68, 127, 241, 108, 132, 160, 80, 210, 227, 20, 230, 69, 201, 127, 87, 8, 28, 137, 238, 37, 239, 80, 147, 55, 2, 17, 0, 0, 0, 2, 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