Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba1f5e132a3195e7d04c6fbb1f1ce31810c1bbe7935ef31746b6fc458b51b128

Tx prefix hash: 7b016d200f5d95acd7105d50fb1227cdd991748cbca167055a5b6b0697412864
Tx public key: 5a8d9e4d4d38f545086b0fb1e990e78aa8f2be486b4e1ae544f5d21ff7da0e30
Timestamp: 1711811243 Timestamp [UCT]: 2024-03-30 15:07:23 Age [y:d:h:m:s]: 00:229:11:23:34
Block: 989692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164242 RingCT/type: yes/0
Extra: 015a8d9e4d4d38f545086b0fb1e990e78aa8f2be486b4e1ae544f5d21ff7da0e3002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5fb83700a1c98a73312c8ca6f893f14ee709004213343531730f4a7785b780a 0.600000000000 1450010 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": 989702, "vin": [ { "gen": { "height": 989692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5fb83700a1c98a73312c8ca6f893f14ee709004213343531730f4a7785b780a" } } ], "extra": [ 1, 90, 141, 158, 77, 77, 56, 245, 69, 8, 107, 15, 177, 233, 144, 231, 138, 168, 242, 190, 72, 107, 78, 26, 229, 68, 245, 210, 31, 247, 218, 14, 48, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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