Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f4c1a4b82f9bfb68315c6c588db43a354f37ac9a5e21ac9d0c4351dde4f7ca1

Tx prefix hash: c8a5deb1723bee25079d28da542541f337552e1f787ccd078aae6beb59cb6fa6
Tx public key: 904e735df4d791e519715e3cb946536b9c7ce4c6d8440df500f1085156f5a17d
Timestamp: 1705117279 Timestamp [UCT]: 2024-01-13 03:41:19 Age [y:d:h:m:s]: 01:073:09:42:33
Block: 934145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313561 RingCT/type: yes/0
Extra: 01904e735df4d791e519715e3cb946536b9c7ce4c6d8440df500f1085156f5a17d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6d25c6eea99ecd5b162956065fc7175d20f8310ae06eec1575d51091924c3f7 0.600000000000 1392133 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": 934155, "vin": [ { "gen": { "height": 934145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6d25c6eea99ecd5b162956065fc7175d20f8310ae06eec1575d51091924c3f7" } } ], "extra": [ 1, 144, 78, 115, 93, 244, 215, 145, 229, 25, 113, 94, 60, 185, 70, 83, 107, 156, 124, 228, 198, 216, 68, 13, 245, 0, 241, 8, 81, 86, 245, 161, 125, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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