Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cee0435fb063b8fd8bf75b97756ce74dc1194167ed0760e3a5ec483450936e9

Tx prefix hash: 0db3d4753eea18b5cac6624a3497517523cad0ca59e6e1280df4505c237edb2a
Tx public key: 7d49998fa14a36dba47e74471fab4b1ab3e6b33a031417acb2f9cc420e2a1826
Timestamp: 1732242357 Timestamp [UCT]: 2024-11-22 02:25:57 Age [y:d:h:m:s]: 00:161:03:29:47
Block: 1158962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114993 RingCT/type: yes/0
Extra: 017d49998fa14a36dba47e74471fab4b1ab3e6b33a031417acb2f9cc420e2a1826021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4d18301d2f20b6e5b10f07df14f2228e8a3437aeef46cdb844d57d2753e2c5d 0.600000000000 1644593 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": 1158972, "vin": [ { "gen": { "height": 1158962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4d18301d2f20b6e5b10f07df14f2228e8a3437aeef46cdb844d57d2753e2c5d" } } ], "extra": [ 1, 125, 73, 153, 143, 161, 74, 54, 219, 164, 126, 116, 71, 31, 171, 75, 26, 179, 230, 179, 58, 3, 20, 23, 172, 178, 249, 204, 66, 14, 42, 24, 38, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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