Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f7dcc1f896945d0f2717e395addc8478cf1c1b62c4a9b18dc947054062e4872

Tx prefix hash: b4be30aa175c8c384e5eccf8f2d32ecf3f96e28d5b2d56c16a2f959da4f524c2
Tx public key: 0f8c0551a98f68b87b7aaad1e5da9c0ec1043000b43b1aba812449a0988e62c9
Timestamp: 1701899261 Timestamp [UCT]: 2023-12-06 21:47:41 Age [y:d:h:m:s]: 01:348:16:27:10
Block: 907490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508081 RingCT/type: yes/0
Extra: 010f8c0551a98f68b87b7aaad1e5da9c0ec1043000b43b1aba812449a0988e62c902110000000233af99f4000000000000000000

1 output(s) for total of 0.604100069000 dcy

stealth address amount amount idx
00: 94fe3b1b8a4fcb4e7066da3f37a31b6cd5d141f111c7a16e5519d71005b232e7 0.604100069000 1364483 of 0

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": 907500, "vin": [ { "gen": { "height": 907490 } } ], "vout": [ { "amount": 604100069, "target": { "key": "94fe3b1b8a4fcb4e7066da3f37a31b6cd5d141f111c7a16e5519d71005b232e7" } } ], "extra": [ 1, 15, 140, 5, 81, 169, 143, 104, 184, 123, 122, 170, 209, 229, 218, 156, 14, 193, 4, 48, 0, 180, 59, 26, 186, 129, 36, 73, 160, 152, 142, 98, 201, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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