Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fb1aa87c7d477cdf085601dc34f7d6aaf38f808f4456f2f3246d6b8d160b078

Tx prefix hash: 11d1b416d136be6f3d74f9087541cc8545672ab3988eeefe75b60a9315385ef5
Tx public key: e764415b85d1cfb1342111bfd10a0d7bfb2ed20073516e1be6b65390134421b3
Timestamp: 1712792326 Timestamp [UCT]: 2024-04-10 23:38:46 Age [y:d:h:m:s]: 00:351:14:14:13
Block: 997776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251382 RingCT/type: yes/0
Extra: 01e764415b85d1cfb1342111bfd10a0d7bfb2ed20073516e1be6b65390134421b302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c3e34eea318a450ee50cd4ddd52bdfd1ed3f69bd3dc2e55c0978e35d17072d4 0.600000000000 1458210 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": 997786, "vin": [ { "gen": { "height": 997776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c3e34eea318a450ee50cd4ddd52bdfd1ed3f69bd3dc2e55c0978e35d17072d4" } } ], "extra": [ 1, 231, 100, 65, 91, 133, 209, 207, 177, 52, 33, 17, 191, 209, 10, 13, 123, 251, 46, 210, 0, 115, 81, 110, 27, 230, 182, 83, 144, 19, 68, 33, 179, 2, 17, 0, 0, 0, 2, 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