Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f655dbec0006462f9a0aab55f9c084c8dcc192d6295c4a3b8461253796331bf3

Tx prefix hash: 1ef799f35cf1e9f29d831232eac05a4a3b70a8c3bbb7906f7d12c031c1fda42e
Tx public key: 0684d2c88468fb9eac39ad120f23ac8165dbdfb02415212ba7b7065bfbea37d4
Timestamp: 1702374272 Timestamp [UCT]: 2023-12-12 09:44:32 Age [y:d:h:m:s]: 01:189:10:40:57
Block: 911443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396441 RingCT/type: yes/0
Extra: 010684d2c88468fb9eac39ad120f23ac8165dbdfb02415212ba7b7065bfbea37d4021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46fc2ead956cdd51314783ade226a2c8e60c99b1918c35d41f777ae34af25f37 0.600000000000 1368645 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": 911453, "vin": [ { "gen": { "height": 911443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46fc2ead956cdd51314783ade226a2c8e60c99b1918c35d41f777ae34af25f37" } } ], "extra": [ 1, 6, 132, 210, 200, 132, 104, 251, 158, 172, 57, 173, 18, 15, 35, 172, 129, 101, 219, 223, 176, 36, 21, 33, 43, 167, 183, 6, 91, 251, 234, 55, 212, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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