Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46ecf78b04d9b100675851b635ed8c3daaa272f6d509645b8f15352462bbcc6d

Tx prefix hash: 4a6b56d9e8e0c15595c13b0c51934dbea5a60759c6fafcbc6724faf7bd3aa1ec
Tx public key: a2d7f11306e42f4376311d30c65ca7d6fc13e5d9fdcd3d4cc071bea09114c0e3
Timestamp: 1699593397 Timestamp [UCT]: 2023-11-10 05:16:37 Age [y:d:h:m:s]: 02:060:14:50:42
Block: 888384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 563182 RingCT/type: yes/0
Extra: 01a2d7f11306e42f4376311d30c65ca7d6fc13e5d9fdcd3d4cc071bea09114c0e3021100000003faf35c9c000000000000000000

1 output(s) for total of 0.698899971000 dcy

stealth address amount amount idx
00: 28b7ca70a299762cbcdb4dfc7d30489665edb36f155bd50df3d697f484739d02 0.698899971000 1344323 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": 888394, "vin": [ { "gen": { "height": 888384 } } ], "vout": [ { "amount": 698899971, "target": { "key": "28b7ca70a299762cbcdb4dfc7d30489665edb36f155bd50df3d697f484739d02" } } ], "extra": [ 1, 162, 215, 241, 19, 6, 228, 47, 67, 118, 49, 29, 48, 198, 92, 167, 214, 252, 19, 229, 217, 253, 205, 61, 76, 192, 113, 190, 160, 145, 20, 192, 227, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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