Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43b3d4073f9f930c11668cc465f84ae9315f64a916cab03c8038c141d25b5089

Tx prefix hash: b937dad07bef860bf4e1c43503ce9d436465db1ec610c72cb996d4e9d99ba616
Tx public key: 9509b09db2f9752e2f92662ab6fc9a704fe8914b7256b5e6eb042d0f67d2311a
Timestamp: 1704621384 Timestamp [UCT]: 2024-01-07 09:56:24 Age [y:d:h:m:s]: 01:089:14:14:53
Block: 930040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325144 RingCT/type: yes/0
Extra: 019509b09db2f9752e2f92662ab6fc9a704fe8914b7256b5e6eb042d0f67d2311a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb3d3aeb3562be18e59890e9fe275944684aef7daff9cb2a0b83eeab16e518c0 0.600000000000 1387918 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": 930050, "vin": [ { "gen": { "height": 930040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb3d3aeb3562be18e59890e9fe275944684aef7daff9cb2a0b83eeab16e518c0" } } ], "extra": [ 1, 149, 9, 176, 157, 178, 249, 117, 46, 47, 146, 102, 42, 182, 252, 154, 112, 79, 232, 145, 75, 114, 86, 181, 230, 235, 4, 45, 15, 103, 210, 49, 26, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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