Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ac304f7127e1bed6b282101fee05af3db4fe54839b3e66764f8e8a134b2283

Tx prefix hash: 21c5d99a67a4e047555885def21697dde5b774fea77daa511f0450a0bb44bb17
Tx public key: 74b71726a58c52e5d8c610e63d860c940ad7bddcac2d87023df6458a754af7ac
Timestamp: 1723547959 Timestamp [UCT]: 2024-08-13 11:19:19 Age [y:d:h:m:s]: 00:216:01:03:24
Block: 1086970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154296 RingCT/type: yes/0
Extra: 0174b71726a58c52e5d8c610e63d860c940ad7bddcac2d87023df6458a754af7ac02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61d8477ba4cd611264001ab3b3ac6efdc2a78654ae5e49ae97df52b4eba990bb 0.600000000000 1561569 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": 1086980, "vin": [ { "gen": { "height": 1086970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61d8477ba4cd611264001ab3b3ac6efdc2a78654ae5e49ae97df52b4eba990bb" } } ], "extra": [ 1, 116, 183, 23, 38, 165, 140, 82, 229, 216, 198, 16, 230, 61, 134, 12, 148, 10, 215, 189, 220, 172, 45, 135, 2, 61, 246, 69, 138, 117, 74, 247, 172, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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