Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03c51af63d636aea92e77e527ac7741238a7c8d83e1b11169995178fbf8aa7e8

Tx prefix hash: 4914fc7fe4f3492794a62c79bcac9a70b7f66fde5b52cc5865e34010bf1e08c0
Tx public key: 895ba03bcc1c6474fb90859d7890ff684a64cb3b30c60b89af29f7f1359639e1
Timestamp: 1702159927 Timestamp [UCT]: 2023-12-09 22:12:07 Age [y:d:h:m:s]: 01:118:14:13:12
Block: 909652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345892 RingCT/type: yes/0
Extra: 01895ba03bcc1c6474fb90859d7890ff684a64cb3b30c60b89af29f7f1359639e1021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e5d6f9aeb0072ad13d6eb22e7b50b456561be9cfc06e18f79ae51a39dbf8b9 0.600000000000 1366755 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": 909662, "vin": [ { "gen": { "height": 909652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e5d6f9aeb0072ad13d6eb22e7b50b456561be9cfc06e18f79ae51a39dbf8b9" } } ], "extra": [ 1, 137, 91, 160, 59, 204, 28, 100, 116, 251, 144, 133, 157, 120, 144, 255, 104, 74, 100, 203, 59, 48, 198, 11, 137, 175, 41, 247, 241, 53, 150, 57, 225, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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