Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c187d4c14dfebaba6e755e0bf07f2a31be87b97c539d2876f085e6c76032e3cb

Tx prefix hash: 4d4a9fabbc958507668717a42a5bb6e3c608c9f2f758d962bb3cf866c2e59a05
Tx public key: 53bd97fee063860af8247ce883b35dfc97fb3236986643dfdd8b930b6bd70b06
Timestamp: 1723291034 Timestamp [UCT]: 2024-08-10 11:57:14 Age [y:d:h:m:s]: 00:227:15:46:16
Block: 1084848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162565 RingCT/type: yes/0
Extra: 0153bd97fee063860af8247ce883b35dfc97fb3236986643dfdd8b930b6bd70b0602110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9d39d82c1ca6c00ba0775d35a62e4068f1ac85d6d24d83dafea362aac9b3b24 0.600000000000 1559271 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": 1084858, "vin": [ { "gen": { "height": 1084848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9d39d82c1ca6c00ba0775d35a62e4068f1ac85d6d24d83dafea362aac9b3b24" } } ], "extra": [ 1, 83, 189, 151, 254, 224, 99, 134, 10, 248, 36, 124, 232, 131, 179, 93, 252, 151, 251, 50, 54, 152, 102, 67, 223, 221, 139, 147, 11, 107, 215, 11, 6, 2, 17, 0, 0, 0, 17, 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