Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9e331593596cdb7910c2b92d37395c7d4b2c55e35e065a8f4e1485c15a48372

Tx prefix hash: ac1e06fe97121c52eb7b994e8688da61b4f0a4b3cdbfef5742e3c7a8a8f37355
Tx public key: 912b7029827412a0b882971484c2ddb28641a0edd91d109f1645e957c109cf18
Timestamp: 1637502814 Timestamp [UCT]: 2021-11-21 13:53:34 Age [y:d:h:m:s]: 03:007:20:47:17
Block: 379009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 784487 RingCT/type: yes/0
Extra: 01912b7029827412a0b882971484c2ddb28641a0edd91d109f1645e957c109cf180211000000021cab2639000000000000000000

1 output(s) for total of 34.058509241000 dcy

stealth address amount amount idx
00: 4f830bd271960bd6cfd6df7e59e9d36c33dbf89b5964dbbceb84ef5a02460d99 34.058509241000 766259 of 0

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": 379019, "vin": [ { "gen": { "height": 379009 } } ], "vout": [ { "amount": 34058509241, "target": { "key": "4f830bd271960bd6cfd6df7e59e9d36c33dbf89b5964dbbceb84ef5a02460d99" } } ], "extra": [ 1, 145, 43, 112, 41, 130, 116, 18, 160, 184, 130, 151, 20, 132, 194, 221, 178, 134, 65, 160, 237, 217, 29, 16, 159, 22, 69, 233, 87, 193, 9, 207, 24, 2, 17, 0, 0, 0, 2, 28, 171, 38, 57, 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