Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e12f2400fb6e6dd0df7d05058adfa6505353fb17d2c104d1677b911ce945a8f9

Tx prefix hash: 14674936fd8b22eb701163789c5cad41bb64959a0806fbd9185dc521d0b04f5c
Tx public key: 60ac7ae045457b5d6788a8a707b3ee41309bdcb03fe05377d0d5d83eded2cb55
Timestamp: 1734078424 Timestamp [UCT]: 2024-12-13 08:27:04 Age [y:d:h:m:s]: 00:132:08:35:34
Block: 1174186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94381 RingCT/type: yes/0
Extra: 0160ac7ae045457b5d6788a8a707b3ee41309bdcb03fe05377d0d5d83eded2cb55021100000001e890f369000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69743ee32d98878a1ffb7f2ab78f4da941e1499b985e56af70e9c035f4f97dcc 0.600000000000 1660305 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": 1174196, "vin": [ { "gen": { "height": 1174186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69743ee32d98878a1ffb7f2ab78f4da941e1499b985e56af70e9c035f4f97dcc" } } ], "extra": [ 1, 96, 172, 122, 224, 69, 69, 123, 93, 103, 136, 168, 167, 7, 179, 238, 65, 48, 155, 220, 176, 63, 224, 83, 119, 208, 213, 216, 62, 222, 210, 203, 85, 2, 17, 0, 0, 0, 1, 232, 144, 243, 105, 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