Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9353ab2301545da0c98396321854b219ab64e16af9ea809e13e99abff949a25

Tx prefix hash: c96e12aa0605c46edf1d6b3d4cff0b5681c8a6e64ac890046e689cc7cdb55ab5
Tx public key: 39e520a10d142da6fc1fb0e20e813ca9170eaaccbed6b735e544c9bc50f57973
Timestamp: 1639500865 Timestamp [UCT]: 2021-12-14 16:54:25 Age [y:d:h:m:s]: 02:339:12:51:37
Block: 395468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 760725 RingCT/type: yes/0
Extra: 0139e520a10d142da6fc1fb0e20e813ca9170eaaccbed6b735e544c9bc50f57973021100000001408d5ef5000000000000000000

1 output(s) for total of 30.036595604000 dcy

stealth address amount amount idx
00: 4fd4d0397d5af7d712e4487148d9196d3a1520afc2df2c7138544ab187fe48d2 30.036595604000 793401 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": 395478, "vin": [ { "gen": { "height": 395468 } } ], "vout": [ { "amount": 30036595604, "target": { "key": "4fd4d0397d5af7d712e4487148d9196d3a1520afc2df2c7138544ab187fe48d2" } } ], "extra": [ 1, 57, 229, 32, 161, 13, 20, 45, 166, 252, 31, 176, 226, 14, 129, 60, 169, 23, 14, 170, 204, 190, 214, 183, 53, 229, 68, 201, 188, 80, 245, 121, 115, 2, 17, 0, 0, 0, 1, 64, 141, 94, 245, 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