Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a79e11ccbd2ccc7a52e579fcfed9ed4fcd7a2f70d023b5279878948e933f6b35

Tx prefix hash: 3a2126e504976e1a40cfe7f756c3d322e67a96aa83ab706cd4b9412faf22e91e
Tx public key: 3f7b3cedfb9e929ec8daa19789498685d3a736954f971dbe4624c97cee35ddb3
Timestamp: 1733442209 Timestamp [UCT]: 2024-12-05 23:43:29 Age [y:d:h:m:s]: 00:328:13:16:57
Block: 1168893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232333 RingCT/type: yes/0
Extra: 013f7b3cedfb9e929ec8daa19789498685d3a736954f971dbe4624c97cee35ddb3021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef247df24ec97aed3da97ce27f6cab41751be7946b3261b1e6c4165e59620634 0.600000000000 1654606 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": 1168903, "vin": [ { "gen": { "height": 1168893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef247df24ec97aed3da97ce27f6cab41751be7946b3261b1e6c4165e59620634" } } ], "extra": [ 1, 63, 123, 60, 237, 251, 158, 146, 158, 200, 218, 161, 151, 137, 73, 134, 133, 211, 167, 54, 149, 79, 151, 29, 190, 70, 36, 201, 124, 238, 53, 221, 179, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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