Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4feb5129f934c3b93d2caeef18513c651d6b46d6c5f85f0c17d1d1ef72dcdc6

Tx prefix hash: 8319233c3e36eacae8a01d6487486cee4c5167d2372053c5075d68a98602809a
Tx public key: 341ee8331036182e44dc258ff0dede1ab96c3d73899a50298aa27df36dbc3ca9
Timestamp: 1717110708 Timestamp [UCT]: 2024-05-30 23:11:48 Age [y:d:h:m:s]: 00:358:04:05:46
Block: 1033599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256035 RingCT/type: yes/0
Extra: 01341ee8331036182e44dc258ff0dede1ab96c3d73899a50298aa27df36dbc3ca902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c6e0f7263932f1b78a804da75384631e04dd6cc75ea1ccd4b8efad78a12ac18 0.600000000000 1502070 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": 1033609, "vin": [ { "gen": { "height": 1033599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c6e0f7263932f1b78a804da75384631e04dd6cc75ea1ccd4b8efad78a12ac18" } } ], "extra": [ 1, 52, 30, 232, 51, 16, 54, 24, 46, 68, 220, 37, 143, 240, 222, 222, 26, 185, 108, 61, 115, 137, 154, 80, 41, 138, 162, 125, 243, 109, 188, 60, 169, 2, 17, 0, 0, 0, 4, 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