Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac7f9a830bd8308cbb92f192bcbcb51f2b3f3b74573745d21d3ea72f69402cbf

Tx prefix hash: 877aebac179451a24efce9afbb521a85885ab7a2baaa144efc0ed4f1806527d8
Tx public key: 4c3b3ebed0be48a74b0c7694e7c5222de2954e19db0002115eb64dcaf2260af1
Timestamp: 1727156691 Timestamp [UCT]: 2024-09-24 05:44:51 Age [y:d:h:m:s]: 00:196:16:39:37
Block: 1116889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140383 RingCT/type: yes/0
Extra: 014c3b3ebed0be48a74b0c7694e7c5222de2954e19db0002115eb64dcaf2260af1021100000003e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 1a5da9ccf79a918eeb84c928a8e0a0e02fc9082e980c0788d71f14485d516d13 0.608000000000 1597528 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": 1116899, "vin": [ { "gen": { "height": 1116889 } } ], "vout": [ { "amount": 608000000, "target": { "key": "1a5da9ccf79a918eeb84c928a8e0a0e02fc9082e980c0788d71f14485d516d13" } } ], "extra": [ 1, 76, 59, 62, 190, 208, 190, 72, 167, 75, 12, 118, 148, 231, 197, 34, 45, 226, 149, 78, 25, 219, 0, 2, 17, 94, 182, 77, 202, 242, 38, 10, 241, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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