Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e432b30a7daf4e9c0130df400d0eb4cb3ef471d1d26b0c362fc09122bb70057

Tx prefix hash: 8e40647aeca8da5aad9bcb8fe3fe06c2d72da9fbb7c3b18023b661f5d1f1b57f
Tx public key: a15121da072ba7c8552943d7116e850e9a19dcd0b79c47928a968bf1bb004cae
Timestamp: 1672107984 Timestamp [UCT]: 2022-12-27 02:26:24 Age [y:d:h:m:s]: 02:316:17:33:33
Block: 661372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745787 RingCT/type: yes/0
Extra: 01a15121da072ba7c8552943d7116e850e9a19dcd0b79c47928a968bf1bb004cae02110000000275e3f0e9000000000000000000

1 output(s) for total of 3.950026282000 dcy

stealth address amount amount idx
00: 8901386780559ab7b99f1cb74013d60726dfa2caf807626b7efd307799618fb5 3.950026282000 1102141 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": 661382, "vin": [ { "gen": { "height": 661372 } } ], "vout": [ { "amount": 3950026282, "target": { "key": "8901386780559ab7b99f1cb74013d60726dfa2caf807626b7efd307799618fb5" } } ], "extra": [ 1, 161, 81, 33, 218, 7, 43, 167, 200, 85, 41, 67, 215, 17, 110, 133, 14, 154, 25, 220, 208, 183, 156, 71, 146, 138, 150, 139, 241, 187, 0, 76, 174, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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