Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7131e651bcdc39af98707ffce98b9e75e62f37382d1ef5dd49cc0cf6be84879

Tx prefix hash: d832fcb4f99e6d27f2a384febad5ee1d994f86fd162d6b9131843c55c27808c9
Tx public key: 7cf62dc8bbc20840bc51d7d5ff48b1c4a1cf9253646c99a7468f8620700063e8
Timestamp: 1734176423 Timestamp [UCT]: 2024-12-14 11:40:23 Age [y:d:h:m:s]: 00:027:09:08:49
Block: 1174993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19567 RingCT/type: yes/0
Extra: 017cf62dc8bbc20840bc51d7d5ff48b1c4a1cf9253646c99a7468f8620700063e8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f9f6d4a11aa384096a874d3c655419c0da70221b3c8d55bacf48bd56ae87389 0.600000000000 1661214 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": 1175003, "vin": [ { "gen": { "height": 1174993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f9f6d4a11aa384096a874d3c655419c0da70221b3c8d55bacf48bd56ae87389" } } ], "extra": [ 1, 124, 246, 45, 200, 187, 194, 8, 64, 188, 81, 215, 213, 255, 72, 177, 196, 161, 207, 146, 83, 100, 108, 153, 167, 70, 143, 134, 32, 112, 0, 99, 232, 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