Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70166213cf85355879ab052cd07ae8d2cafd31af6c2a86d3b4049cb8f78266e1

Tx prefix hash: 9a82c8dcd1042c7038d8d31892e801c61a2e2a38d5193ae420346cad9b65650f
Tx public key: 1c56d219ed18339ad9cf0b7986ee7238aae97fd803ad716a61f5f07674f5c6a9
Timestamp: 1634797065 Timestamp [UCT]: 2021-10-21 06:17:45 Age [y:d:h:m:s]: 03:114:20:21:24
Block: 357260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 860093 RingCT/type: yes/0
Extra: 011c56d219ed18339ad9cf0b7986ee7238aae97fd803ad716a61f5f07674f5c6a90211000000bb8d0de867000000000000000000

1 output(s) for total of 40.202191436000 dcy

stealth address amount amount idx
00: 9f260a7f4d69977cb83449ec68975a4d4064dd7e40c67a1e81e8e027e55e7535 40.202191436000 728556 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": 357270, "vin": [ { "gen": { "height": 357260 } } ], "vout": [ { "amount": 40202191436, "target": { "key": "9f260a7f4d69977cb83449ec68975a4d4064dd7e40c67a1e81e8e027e55e7535" } } ], "extra": [ 1, 28, 86, 210, 25, 237, 24, 51, 154, 217, 207, 11, 121, 134, 238, 114, 56, 170, 233, 127, 216, 3, 173, 113, 106, 97, 245, 240, 118, 116, 245, 198, 169, 2, 17, 0, 0, 0, 187, 141, 13, 232, 103, 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