Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84e828970f86b1cf0b705633d6dc631692bd6c499f65394984e9c04bbaef3a35

Tx prefix hash: 55b6f3d457ca35b4f7deb0d5515c52996ed137fa3b5a580a849f0469cdcb8dbf
Tx public key: 0ce4083d5dc0bc6332cec609ddee73e0471ad82adfeeeca1b6ad7467c95a56f1
Timestamp: 1710135880 Timestamp [UCT]: 2024-03-11 05:44:40 Age [y:d:h:m:s]: 01:243:13:56:13
Block: 975785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432798 RingCT/type: yes/0
Extra: 010ce4083d5dc0bc6332cec609ddee73e0471ad82adfeeeca1b6ad7467c95a56f102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 383d9c7004df209ad8a4a4a7d8457a805418889f6d06275b01115b0c5c38c277 0.600000000000 1435760 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": 975795, "vin": [ { "gen": { "height": 975785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "383d9c7004df209ad8a4a4a7d8457a805418889f6d06275b01115b0c5c38c277" } } ], "extra": [ 1, 12, 228, 8, 61, 93, 192, 188, 99, 50, 206, 198, 9, 221, 238, 115, 224, 71, 26, 216, 42, 223, 238, 236, 161, 182, 173, 116, 103, 201, 90, 86, 241, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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