Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ff2a5f5af9c7a67f9d95796bf564db8ba8b715094d5809e77903f3c270093e2

Tx prefix hash: 54c54e68d844a53a8549eef4635b40d7b5834470a75ee24a92bd9c1e5908416a
Tx public key: b8f9e8c9dd9f85063dcdef8fbee133f3a6657b8394f79349cffc0531a0425853
Timestamp: 1705659459 Timestamp [UCT]: 2024-01-19 10:17:39 Age [y:d:h:m:s]: 01:041:00:00:02
Block: 938627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290377 RingCT/type: yes/0
Extra: 01b8f9e8c9dd9f85063dcdef8fbee133f3a6657b8394f79349cffc0531a04258530211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57c07e5964e7cfbad4c6ee205d62fddd51e7ef48fd14be6aea071a61fb2cdbdb 0.600000000000 1396697 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": 938637, "vin": [ { "gen": { "height": 938627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57c07e5964e7cfbad4c6ee205d62fddd51e7ef48fd14be6aea071a61fb2cdbdb" } } ], "extra": [ 1, 184, 249, 232, 201, 221, 159, 133, 6, 61, 205, 239, 143, 190, 225, 51, 243, 166, 101, 123, 131, 148, 247, 147, 73, 207, 252, 5, 49, 160, 66, 88, 83, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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