Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 736357127d636e9096c4028333e11774283b2712b0019af7fe5b2ae1e7f9cf6d

Tx prefix hash: 69b63f01a3592109a3bf34743e29a193fff850e8537b5c247613e69fcba7686e
Tx public key: 10e4e3fc6b2fc90317fcb4831cbb31cd7ec1728f92ce77d842eff89f147d64d3
Timestamp: 1576424052 Timestamp [UCT]: 2019-12-15 15:34:12 Age [y:d:h:m:s]: 05:321:00:56:10
Block: 27261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1374069 RingCT/type: yes/0
Extra: 0110e4e3fc6b2fc90317fcb4831cbb31cd7ec1728f92ce77d842eff89f147d64d3021100000018ad433a0b000000000000000000

1 output(s) for total of 498.509979491000 dcy

stealth address amount amount idx
00: bc44bf4fdc079ce425d59bdbceb3e253b36b7cfc5bdd373eade1f3ed9799cbc8 498.509979491000 45249 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": 27271, "vin": [ { "gen": { "height": 27261 } } ], "vout": [ { "amount": 498509979491, "target": { "key": "bc44bf4fdc079ce425d59bdbceb3e253b36b7cfc5bdd373eade1f3ed9799cbc8" } } ], "extra": [ 1, 16, 228, 227, 252, 107, 47, 201, 3, 23, 252, 180, 131, 28, 187, 49, 205, 126, 193, 114, 143, 146, 206, 119, 216, 66, 239, 248, 159, 20, 125, 100, 211, 2, 17, 0, 0, 0, 24, 173, 67, 58, 11, 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