Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15cd1985c9949c407357d40bdcc09f15e045bc3aa77f2052bfe6d8a10e5e9d91

Tx prefix hash: 4e87bb698047a49e9824ccd48bc5d950ee34ae7c189925b93dc805be839c9036
Tx public key: 6d1b860ab87546bb8463ab3e6be4a3b466932a59c6f60483461d7307031b9e13
Timestamp: 1706418946 Timestamp [UCT]: 2024-01-28 05:15:46 Age [y:d:h:m:s]: 01:309:18:33:28
Block: 944940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480234 RingCT/type: yes/0
Extra: 016d1b860ab87546bb8463ab3e6be4a3b466932a59c6f60483461d7307031b9e1302110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b70b99c4b3e10cb94778a45d903c2f3e4509997ad951162fac1eaa15dc8b5605 0.600000000000 1403238 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": 944950, "vin": [ { "gen": { "height": 944940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b70b99c4b3e10cb94778a45d903c2f3e4509997ad951162fac1eaa15dc8b5605" } } ], "extra": [ 1, 109, 27, 134, 10, 184, 117, 70, 187, 132, 99, 171, 62, 107, 228, 163, 180, 102, 147, 42, 89, 198, 246, 4, 131, 70, 29, 115, 7, 3, 27, 158, 19, 2, 17, 0, 0, 0, 10, 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