Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1dc40c5fa5ab1962dce832dc86eadaad097a673ef161e5d31ebe07228c0d98f

Tx prefix hash: 3d33ebf067ebbf59a95daecfbff10d0747a108d2cfcf1c3a808b66d99f2d75f5
Tx public key: 385ff8eafc6640a5acd2bf3d296ab1442290bfcffb079d2dc22a1a54f08d0910
Timestamp: 1712793998 Timestamp [UCT]: 2024-04-11 00:06:38 Age [y:d:h:m:s]: 00:266:22:08:38
Block: 997787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191097 RingCT/type: yes/0
Extra: 01385ff8eafc6640a5acd2bf3d296ab1442290bfcffb079d2dc22a1a54f08d091002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6f11bc571980c117b210fecc216f9e9f38d78d28c0102edc97f1012cb4bdeeb 0.600000000000 1458221 of 15

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": 997797, "vin": [ { "gen": { "height": 997787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6f11bc571980c117b210fecc216f9e9f38d78d28c0102edc97f1012cb4bdeeb" } } ], "extra": [ 1, 56, 95, 248, 234, 252, 102, 64, 165, 172, 210, 191, 61, 41, 106, 177, 68, 34, 144, 191, 207, 251, 7, 157, 45, 194, 42, 26, 84, 240, 141, 9, 16, 2, 17, 0, 0, 0, 2, 89, 218, 211, 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