Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1af8d0d579af1fbd0049df1f8454998afecf0df6d649aa2ad38c7812669817b1

Tx prefix hash: 00e8f06573023796da005d70cda180014ec530913d1a2af4da5c0e99016c4387
Tx public key: 97993cbc1b8f607e9ff252eae4582d60881b411acd4f58fbce2a98d8af43cfe0
Timestamp: 1721908167 Timestamp [UCT]: 2024-07-25 11:49:27 Age [y:d:h:m:s]: 00:276:20:44:36
Block: 1073371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197810 RingCT/type: yes/0
Extra: 0197993cbc1b8f607e9ff252eae4582d60881b411acd4f58fbce2a98d8af43cfe002110000001be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ec01fb170221601845cb697e2c8b534a31ddc51c0a16fb5012dcf221a51665a 0.600000000000 1545872 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": 1073381, "vin": [ { "gen": { "height": 1073371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ec01fb170221601845cb697e2c8b534a31ddc51c0a16fb5012dcf221a51665a" } } ], "extra": [ 1, 151, 153, 60, 188, 27, 143, 96, 126, 159, 242, 82, 234, 228, 88, 45, 96, 136, 27, 65, 26, 205, 79, 88, 251, 206, 42, 152, 216, 175, 67, 207, 224, 2, 17, 0, 0, 0, 27, 233, 20, 221, 21, 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