Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 750f0b9471a696cccaf0c8e4367cfeeea5de60949c278b0474d2246b045df06a

Tx prefix hash: cf0bcb0b3599d7aeaeb8d3c3b7063c2dfb7d6fbbe3824ea8384993985d43ccb4
Tx public key: 6c74d2e0cdeeb94b86dc712f6f8357d2af6abd0ed69fc57254194d37c9fbd191
Timestamp: 1735883522 Timestamp [UCT]: 2025-01-03 05:52:02 Age [y:d:h:m:s]: 00:070:10:06:58
Block: 1189119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50111 RingCT/type: yes/0
Extra: 016c74d2e0cdeeb94b86dc712f6f8357d2af6abd0ed69fc57254194d37c9fbd191021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69d22ff9c628855213e97ef54c27dc39aa4ad9f300d4d5c8de5aeb8d6f0eb2f6 0.600000000000 1675624 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": 1189129, "vin": [ { "gen": { "height": 1189119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69d22ff9c628855213e97ef54c27dc39aa4ad9f300d4d5c8de5aeb8d6f0eb2f6" } } ], "extra": [ 1, 108, 116, 210, 224, 205, 238, 185, 75, 134, 220, 113, 47, 111, 131, 87, 210, 175, 106, 189, 14, 214, 159, 197, 114, 84, 25, 77, 55, 201, 251, 209, 145, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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