Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80f9d3a89eef21f5e7de177d4231e134680be407f1255abc6ebf8bb282a8e4ed

Tx prefix hash: 7ed53758b21fae258878503dbd0e79842db5dfa57e8564e09a9bdf0ce5dd4fec
Tx public key: 5823d862779431b13af2ae5a2cba4b0a580fd70d129a36f4102d6828fa0981ae
Timestamp: 1724992566 Timestamp [UCT]: 2024-08-30 04:36:06 Age [y:d:h:m:s]: 01:124:14:35:39
Block: 1098937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347574 RingCT/type: yes/0
Extra: 015823d862779431b13af2ae5a2cba4b0a580fd70d129a36f4102d6828fa0981ae02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 029bf7b90b695b0bba133715a831586bd6b790ce9d8f89cb74a31b20af24b4d2 0.600000000000 1574826 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": 1098947, "vin": [ { "gen": { "height": 1098937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "029bf7b90b695b0bba133715a831586bd6b790ce9d8f89cb74a31b20af24b4d2" } } ], "extra": [ 1, 88, 35, 216, 98, 119, 148, 49, 177, 58, 242, 174, 90, 44, 186, 75, 10, 88, 15, 215, 13, 18, 154, 54, 244, 16, 45, 104, 40, 250, 9, 129, 174, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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