Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f8ffb5875fa77c9e346a538b54558bc14eed5d49090ae86062995fef3cc4699

Tx prefix hash: 88f790d74bfcd0280c0bf7eabea473566f9e5a07c601a88aad3fd19af9d522a6
Tx public key: 505673b1fddd546747583b3837be01aab5712c2be8dabc38a48b4f1fb8343f4c
Timestamp: 1681624384 Timestamp [UCT]: 2023-04-16 05:53:04 Age [y:d:h:m:s]: 02:061:06:26:13
Block: 739640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565884 RingCT/type: yes/0
Extra: 01505673b1fddd546747583b3837be01aab5712c2be8dabc38a48b4f1fb8343f4c02110000000233af99f4000000000000000000

1 output(s) for total of 2.174031634000 dcy

stealth address amount amount idx
00: 8ab59c252822f23e2609fc22e11fcead1faf53c21d2f0edb6d8abc7bc4d4ee03 2.174031634000 1186503 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": 739650, "vin": [ { "gen": { "height": 739640 } } ], "vout": [ { "amount": 2174031634, "target": { "key": "8ab59c252822f23e2609fc22e11fcead1faf53c21d2f0edb6d8abc7bc4d4ee03" } } ], "extra": [ 1, 80, 86, 115, 177, 253, 221, 84, 103, 71, 88, 59, 56, 55, 190, 1, 170, 181, 113, 44, 43, 232, 218, 188, 56, 164, 139, 79, 31, 184, 52, 63, 76, 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