Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43909d4df7b4dda30cf0cee6b1d073124bc40011062a48a0fe25bbf3dc2bf25c

Tx prefix hash: 805a67ac1902560dd2ddd9d7afd4e961a60575244465a584ebc4b84784116a6d
Tx public key: a6817c3704f47e69645aba47eb34680176fa48cb5db0d6d8464a4d9f54f2004e
Timestamp: 1689558001 Timestamp [UCT]: 2023-07-17 01:40:01 Age [y:d:h:m:s]: 01:289:23:53:18
Block: 805440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468385 RingCT/type: yes/0
Extra: 01a6817c3704f47e69645aba47eb34680176fa48cb5db0d6d8464a4d9f54f2004e021100000003faf35c9c000000000000000000

1 output(s) for total of 1.315961089000 dcy

stealth address amount amount idx
00: 1c872450aa0f45be9257e8c90cbf8ee37661e01fa23d49d8c9c2efd2234d93a4 1.315961089000 1256667 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": 805450, "vin": [ { "gen": { "height": 805440 } } ], "vout": [ { "amount": 1315961089, "target": { "key": "1c872450aa0f45be9257e8c90cbf8ee37661e01fa23d49d8c9c2efd2234d93a4" } } ], "extra": [ 1, 166, 129, 124, 55, 4, 244, 126, 105, 100, 90, 186, 71, 235, 52, 104, 1, 118, 250, 72, 203, 93, 176, 214, 216, 70, 74, 77, 159, 84, 242, 0, 78, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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