Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70f30d275fc0b40ede29779235b419f49f51a4d77f7d1bedfee595861148d75a

Tx prefix hash: 16a114feebca4b4cd0c7ed3be5ba1defc46f5c5132c6246d78dfde992b067a2f
Tx public key: c4f53955089d4a8686845dd70dd5a730f1d3c7100b64e5a9c750ccadb7e04983
Timestamp: 1720007321 Timestamp [UCT]: 2024-07-03 11:48:41 Age [y:d:h:m:s]: 00:274:14:19:16
Block: 1057619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196188 RingCT/type: yes/0
Extra: 01c4f53955089d4a8686845dd70dd5a730f1d3c7100b64e5a9c750ccadb7e0498302110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdb86b69a88a67fafa023869b3b37fa390a70ad2f6abd2d82fd9520ef35dc215 0.600000000000 1528056 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": 1057629, "vin": [ { "gen": { "height": 1057619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdb86b69a88a67fafa023869b3b37fa390a70ad2f6abd2d82fd9520ef35dc215" } } ], "extra": [ 1, 196, 245, 57, 85, 8, 157, 74, 134, 134, 132, 93, 215, 13, 213, 167, 48, 241, 211, 199, 16, 11, 100, 229, 169, 199, 80, 204, 173, 183, 224, 73, 131, 2, 17, 0, 0, 0, 12, 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