Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d150622d151e4ddbe2f2e4d175a165fd9ae0517704941d815ef3f20686e959f2

Tx prefix hash: a377a1753e058aea12601d7cbd36cff61fb3da7fcc4221676f18ded052b68ddb
Tx public key: a274c70afaa555d6a0baa7c93fbb3775de2dc34a2046dea742d08aa2fe396748
Timestamp: 1683729088 Timestamp [UCT]: 2023-05-10 14:31:28 Age [y:d:h:m:s]: 02:182:04:43:02
Block: 757110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 650023 RingCT/type: yes/0
Extra: 01a274c70afaa555d6a0baa7c93fbb3775de2dc34a2046dea742d08aa2fe39674802110000000475e3f0e9000000000000000000

1 output(s) for total of 1.902744483000 dcy

stealth address amount amount idx
00: f44aee0c1ac26f15870243f41f258798ce7baf66621c4f7dced6507bfa789c39 1.902744483000 1205517 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": 757120, "vin": [ { "gen": { "height": 757110 } } ], "vout": [ { "amount": 1902744483, "target": { "key": "f44aee0c1ac26f15870243f41f258798ce7baf66621c4f7dced6507bfa789c39" } } ], "extra": [ 1, 162, 116, 199, 10, 250, 165, 85, 214, 160, 186, 167, 201, 63, 187, 55, 117, 222, 45, 195, 74, 32, 70, 222, 167, 66, 208, 138, 162, 254, 57, 103, 72, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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