Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 874e41d3632b0d9e16e36031ddb14b16624afd41fd60967409ec95a76b4e90cc

Tx prefix hash: b2640dfb95fc10a1cc8f54aa9af54c525bc7f569538d6a51f8b5114753fd5b0f
Tx public key: f66df81769baa7a0cdb4cbd9c31c91f5b008d176af2143533317b194f1324cf8
Timestamp: 1736103494 Timestamp [UCT]: 2025-01-05 18:58:14 Age [y:d:h:m:s]: 00:161:17:53:07
Block: 1190923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115328 RingCT/type: yes/0
Extra: 01f66df81769baa7a0cdb4cbd9c31c91f5b008d176af2143533317b194f1324cf802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae7f386718afd81f4cee66c1ba4347492ca3e3addc55cee8dd4dd025aab49915 0.600000000000 1677446 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": 1190933, "vin": [ { "gen": { "height": 1190923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae7f386718afd81f4cee66c1ba4347492ca3e3addc55cee8dd4dd025aab49915" } } ], "extra": [ 1, 246, 109, 248, 23, 105, 186, 167, 160, 205, 180, 203, 217, 195, 28, 145, 245, 176, 8, 209, 118, 175, 33, 67, 83, 51, 23, 177, 148, 241, 50, 76, 248, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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