Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b18840d2fd38c864ec2b2c9be5a5c2f79a934f826d99a6fa818b46ef48271d6e

Tx prefix hash: a03f6a2eb0ca3f880ad1018d340a73eb76c1dd75eac9ce06d3068e39ed08594e
Tx public key: 7d229031415dacaa2c743acd723ce49b777bead3c290bb894673e11fac140363
Timestamp: 1697417203 Timestamp [UCT]: 2023-10-16 00:46:43 Age [y:d:h:m:s]: 01:140:03:06:00
Block: 870533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361159 RingCT/type: yes/0
Extra: 017d229031415dacaa2c743acd723ce49b777bead3c290bb894673e11fac14036302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.800901469000 dcy

stealth address amount amount idx
00: 9fd15d8745c4b33cbdac1c6e31f55ddc358d730e85289035f22d40a9489e4f16 0.800901469000 1325412 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": 870543, "vin": [ { "gen": { "height": 870533 } } ], "vout": [ { "amount": 800901469, "target": { "key": "9fd15d8745c4b33cbdac1c6e31f55ddc358d730e85289035f22d40a9489e4f16" } } ], "extra": [ 1, 125, 34, 144, 49, 65, 93, 172, 170, 44, 116, 58, 205, 114, 60, 228, 155, 119, 123, 234, 211, 194, 144, 187, 137, 70, 115, 225, 31, 172, 20, 3, 99, 2, 17, 0, 0, 0, 2, 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