Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6123e35050f50a91ff248891531f883edcbe84394cbf1bce0c11a5374d3317d1

Tx prefix hash: 6fd8ca58b334abfbfd6ed2d0d705178eaeabf9e66a541f6bed184fcbb4f6fed4
Tx public key: 1c46e081d6c4e08d6b8b9ccae563bf3fd9d163afb6ba9a4df18331167ea3e4ba
Timestamp: 1712601307 Timestamp [UCT]: 2024-04-08 18:35:07 Age [y:d:h:m:s]: 00:267:20:27:37
Block: 996184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191765 RingCT/type: yes/0
Extra: 011c46e081d6c4e08d6b8b9ccae563bf3fd9d163afb6ba9a4df18331167ea3e4ba02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f2a9db91828ea316b2c7ac5ad47043e5f6dfa206475c119ffe945754b312883 0.600000000000 1456600 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": 996194, "vin": [ { "gen": { "height": 996184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f2a9db91828ea316b2c7ac5ad47043e5f6dfa206475c119ffe945754b312883" } } ], "extra": [ 1, 28, 70, 224, 129, 214, 196, 224, 141, 107, 139, 156, 202, 229, 99, 191, 63, 217, 209, 99, 175, 182, 186, 154, 77, 241, 131, 49, 22, 126, 163, 228, 186, 2, 17, 0, 0, 0, 4, 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