Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 745d6f36fca7250bc684b0c3b554ad0f008f35708a34e1c82f224ee9d0cd9999

Tx prefix hash: 041125a1a5a3070ed3c7bacbd08389e0d9acc9af49a18015e7ef7c07d134bb85
Tx public key: 0f04dddc9b411a03f7224abee99e07fed6177ac7a9c7be1b85d78bf7816557d4
Timestamp: 1613682339 Timestamp [UCT]: 2021-02-18 21:05:39 Age [y:d:h:m:s]: 03:323:18:26:58
Block: 201706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 990557 RingCT/type: yes/0
Extra: 010f04dddc9b411a03f7224abee99e07fed6177ac7a9c7be1b85d78bf7816557d4021100000005c6b81c9d000000000000000000

1 output(s) for total of 131.726280074000 dcy

stealth address amount amount idx
00: 540b04eb4109d2dc3639fa0811dd62358e8552421d5bc9136abe1cf2129160dc 131.726280074000 412750 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": 201716, "vin": [ { "gen": { "height": 201706 } } ], "vout": [ { "amount": 131726280074, "target": { "key": "540b04eb4109d2dc3639fa0811dd62358e8552421d5bc9136abe1cf2129160dc" } } ], "extra": [ 1, 15, 4, 221, 220, 155, 65, 26, 3, 247, 34, 74, 190, 233, 158, 7, 254, 214, 23, 122, 199, 169, 199, 190, 27, 133, 215, 139, 247, 129, 101, 87, 212, 2, 17, 0, 0, 0, 5, 198, 184, 28, 157, 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